PDA

View Full Version : Cambridge 302 learning curve cont.


Tuno
July 4th 04, 04:09 AM
I flew with mine for the first time today, and it communicated fine with
WinPilot Pro, but I had a problem with the speed-to-fly function. No matter
how bad the sink, now matter how slow I flew, it kept telling me to fly
slower.

Also, the vario needle disagreed wildly with my Borgelt B-40. Like they were
in different gliders on different days. I couldn't make a correlation
between the two.

I'm going to double-check the polar setting in the morning but I'm 99%
certain it's correct. Any other ideas?

~2NO in Hobbs

Mark Zivley
July 4th 04, 02:16 PM
Tuno,

Are you using the electronic TE? If so, did you pipe the TE and Static
ports together? If you are using the TE input, is the electronic TE set
to 0?

Also, check your pneumatic connections. You can pop the sliding canopy
window open and closed to see if the air pressure change in the cockpit
can affect the vario which would indicate a leak.

Our 302 operating on the TE input that is shared w/ our B40 agree quite
well. Get the piping sorted out first and then see if the polar/speed
to fly works better.

Mark

Tuno wrote:
> I flew with mine for the first time today, and it communicated fine with
> WinPilot Pro, but I had a problem with the speed-to-fly function. No matter
> how bad the sink, now matter how slow I flew, it kept telling me to fly
> slower.
>
> Also, the vario needle disagreed wildly with my Borgelt B-40. Like they were
> in different gliders on different days. I couldn't make a correlation
> between the two.
>
> I'm going to double-check the polar setting in the morning but I'm 99%
> certain it's correct. Any other ideas?
>
> ~2NO in Hobbs
>
>

Kevin Christner
July 4th 04, 05:36 PM
"Tuno" > wrote in message >...
> I flew with mine for the first time today, and it communicated fine with
> WinPilot Pro, but I had a problem with the speed-to-fly function. No matter
> how bad the sink, now matter how slow I flew, it kept telling me to fly
> slower.
>
> Also, the vario needle disagreed wildly with my Borgelt B-40. Like they were
> in different gliders on different days. I couldn't make a correlation
> between the two.
>
> I'm going to double-check the polar setting in the morning but I'm 99%
> certain it's correct. Any other ideas?
>
> ~2NO in Hobbs

Are you running them both of the same TE line? If you split the line
too close to the varios, they will interfere with each other causing
"jumpiness"

Also, if you are using electronic compensation for the 302, have you
tried adjusting this?

Tuno
July 5th 04, 05:14 AM
> Are you running them both of the same TE line? If you split the line
> too close to the varios, they will interfere with each other causing
> "jumpiness"

Yes they use the same TE line, each has about 4" of lead from the "T" split.
I have no idea if that's "too close" to the varios...

> Also, if you are using electronic compensation for the 302, have you
> tried adjusting this?

I have the TE line connected to the 302, so I guess the answer to this
question is no, I'm not using electronic compensationl. The parameter on
page 9 (or is it 10?) for this is set to 0.

This morning I tweaked some settings using the PC software, and subsequently
the vario function worked properly, including reading zero on bootup.
However the speed to fly function is still nonfunctional. It wants me to
fly, like, zero knots or something. I triple and quadruple checked all the
settings so I'm pretty much stumped on this one.

2NO

Peter
July 5th 04, 10:10 AM
Are you running them both of the same TE line? If you split the line
> too close to the varios, they will interfere with each other causing
> "jumpiness"

This is wrong. Neither the 302 nor the B40 use flask(s) so there is no
flow and therefore no interference. You can connect them togeather
with no risk of interference.

One reason why the 302 needle can be way off is if there is sunlight
on the display when you power up. The sunlight can disturb the optical
sensors that detect the needle. You can see this when you power off -
if the needle does not return to 0 then it was incorrectly detected at
power up. make sure the 302 display is in shadow when you power up (eg
using your hand).

Peter

Google